Mapping in mobile data collection systems, such as for utility meter reading and related applications

ABSTRACT

A mobile data collection system may perform or facilitate monitoring and management of mobile automatic meter reading (MAMR) activities via out of route meter read identification and graphical route playback. In identifying out of route endpoints, the mobile data collection system receives an indication of each of the endpoints included in a predetermined meter reading route. The mobile data collection system executes the route detecting endpoints and collecting location information relating to out of route endpoints that are not included in the predetermined route. Location information identifying the out of route endpoints is then presented to a user. In facilitating graphical route playback, the mobile data collection system collects information as it progresses through the route. The collected information may then be used in a graphical playback of the route, which shows the mobile data collection system dynamically traveling through the route (e.g., on a map) and reading endpoints.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.10/903,866, filed Jul. 30, 2004 (now U.S. Pat. No. 7,283,062) whichclaims priority to commonly owned U.S. Provisional Patent ApplicationNo. 60/592,053, also entitled “Mapping in Mobile Data CollectionSystems, Such as for Utility Meter Reading and Related Applications,”filed Jul. 28, 2004, which applications are herein incorporated byreference.

BACKGROUND

Utility companies typically rely on meter reading to determineconsumption of a utility by its customers. In some utility meter readingapplications, operators drive vehicles equipped with radio-equipped datacollection units around an area or route to read electric, gas, and/orwater meters. The meters are equipped with modules that allow them tosend and receive signals. This style of meter reading, sometimesreferred to as mobile automatic meter reading (MAMR), allows meterreading to be completed without direct access to the meter.

MAMR is sometimes used in saturated areas where there may be largepopulations of meters, difficult-to-access meters, or hazardous-to-readmeters. When used in such areas, MAMR can dramatically improve meterreading efficiency. For example, a single data command unit transceiverreads an average of 10,000-12,000 meters in an eight-hour shift, and canread up to 24,000 meters per day, depending on meter density and systemuse.

Routes for MAMR are typically defined geographically and may includehundreds or thousands of meters. The meters on the route are read usingone or more techniques. For example, with a wake-up technique, a MAMRvehicle moves through an area and sends wakeup signals to notify themeters in the area to send meter reading data. With a bubble-uptechnique, the MAMR vehicle simply picks up broadcasted signals from allmeters in its vicinity. To determine the endpoints in a route, MAMRsystems typically rely on route information provided by the utility. Insome cases, the route information includes a list that identifies eachmeter using a unique meter ID and address assigned to the meter. Theroute information is typically formulated in advance of driving theroute, and is often based on the geographic location of each meterrelative to other meters in the route. For example, a MAMR route mayhave starting and ending points, and meters are read according toproximity from a vehicle moving between the starting and ending points.

Routes consisting of lists of meter addresses are typically provided inadvance of MAMR activities. Because of this, and because of many otherreasons, route planners, MAMR operators, utilities, and their customerscould benefit from improvements in monitoring and mapping capabilitiesin MAMR systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing an example of a system for performingmobile collection of meter reading data, including identifying out ofroute meters and facilitating playback of graphical route informationunder one embodiment.

FIG. 2 is a block diagram showing an example implementation of themobile data collection system of FIG. 1.

FIG. 3 is a display diagram showing a dashboard view associated with themobile data collection system of FIGS. 1 and 2.

FIG. 4 is a display diagram showing mapping symbology associated with amapping component of the mobile data collection system of FIGS. 1 and 2.

FIG. 5 is a display diagram showing mapped endpoints associated with themapping component of the mobile data collection system of FIGS. 1 and 2.

FIG. 6 is a display diagram showing a second map of endpoints associatedwith the mapping component of the mobile data collection system of FIGS.1 and 2.

FIG. 7 is a display diagram showing map and zooming features associatedwith the mapping component of the mobile data collection system of FIGS.1 and 2.

FIG. 8 is a display diagram showing an out of route view associated withthe mobile data collection system of FIGS. 1 and 2.

FIG. 9 is a display diagram showing importing a route file to be viewedin association with the route playback component of the mobile datacollection system of FIGS. 1 and 2.

FIGS. 10 and 11 are display diagrams showing playback of a route inassociation with the route playback component of the mobile datacollection system of FIGS. 1 and 2.

FIG. 12 is a block diagram showing an example of a data structure usedin route playback.

FIG. 13 is a flow chart showing an example of a routine for identifyingand displaying out of route endpoints, which is performed at the mobiledata collection system of FIGS. 1 and 2.

FIG. 14 is a flow chart showing a logging routine for a route playbackperformed at the mobile data collection system of FIGS. 1 and 2.

FIG. 15 is a flow chart showing a route playback routine.

In the drawings, the same reference numbers identify identical orsubstantially similar elements or acts. To facilitate the discussion ofany particular element or act, the most significant digit or digits in areference number refer to the figure number in which that element isfirst introduced (e.g., element 204 is first introduced and discussedwith respect to FIG. 2).

A portion of this disclosure contains material to which a claim forcopyright is made. The copyright owner has no objection to the facsimilereproduction by anyone of the patent document or patent disclosure(including Figures), as it appears in the Patent and Trademark Officepatent file or records, but reserves all other copyright rightswhatsoever.

DETAILED DESCRIPTION

The invention will now be described with respect to various embodiments.The following description provides specific details for a thoroughunderstanding of, and enabling description for, these embodiments of theinvention. However, one skilled in the art will understand that theinvention may be practiced without these details. In other instances,well-known structures and functions have not been shown or described indetail to avoid unnecessarily obscuring the description of theembodiments of the invention.

It is intended that the terminology used in the description presented beinterpreted in its broadest reasonable manner, even though it is beingused in conjunction with a detailed description of certain specificembodiments of the invention. Certain terms may even be emphasizedbelow; however, any terminology intended to be interpreted in anyrestricted manner will be overtly and specifically defined as such inthis Detailed Description section.

I. Overview

The method and system described herein allows for monitoring andmanagement of mobile automatic meter reading (MAMR) activities via outof route meter read identification and graphical route playback. In someembodiments, some of the monitoring and management activities occur at amobile data collection system. The mobile data collection system mayinclude a combination of components (including both hardware andsoftware) that generally facilitate the collection of meter data fromutility meters (e.g., electric, gas, water, etc.) and the graphicaldisplay of meter routes in progress via the use of maps or otherfeatures.

In some embodiments, the mobile data collection system may be configuredto identify and record information relating to out of route meters(e.g., meters not associated with a route presently known by the mobiledata collection system). Such meters (or “endpoints”) may beunexpectedly, inadvertently, unintentionally, or otherwise, encounteredduring a meter reading route. In the event of an out of route endpoint,the mobile data collection system may alert an operator of the mobiledata collection system. For example, the mobile data collection systemmay display information relating to each of the out of route endpointson the route and/or may provide an audible alert when such a meter isencountered.

Information relating to the reading of out of route endpoints on theroute may include the physical location of each of the encountered outof route endpoints and the physical location of the vehicle at the timethe endpoint was read. The same information may be provided for in routeendpoints. The mobile data collection system may provide thisinformation to the operator using a map and/or in another formats, suchas in text on a list or other display. While driving the route, theoperator may use the information relating to the out of route endpointsto make decisions about how to drive the route. In some embodiments, themobile data collection system may automatically determine an optimizeddriving path for the operator based on the collected out of routeendpoint information. The automatic determination of an optimizeddriving path may be based on mathematical computations and algorithmsapplied to the collected information, including information about theroute, the vehicle, the endpoints, etc.

In addition, the mobile data collection system may provide informationrelating to the out of route endpoints to a host processing system, orany other system configured for further processing of the information.The utility service provider may then use this information toreconfigure or optimize meter reading routes and to otherwise increasethe efficiency of the mobile collection system. For example, theinformation related to out of route meters may be used to automaticallydetermine which endpoints to include within predetermined routes, thusreducing the number of out of route endpoints encountered on each route.Information about out of route endpoints may also be of use when autility is managing the billing of off cycle reads, which are oftenassociated with customers that are moving.

The mobile data collection system may also log route data so that it canbe played back after the route is completed. For example, the mobiledata collection system may provide a map showing the path that thevehicle took during the route, the order that the meters were read, thetiming of the route, etc. The type of information displayed on the mapmay include the location of the vehicles, the reading of meters orgroups of meters, the identification of in route and out of routemeters, etc. This information may be used for almost any purpose,including training, supervision of employees, improving routeefficiency, assisting contractors or substitute meter readers, routeoptimization, etc.

II. Representative System

FIG. 1 and the following discussion provide a brief, general descriptionof a suitable environment in which the invention can be implemented.Although not required, aspects of the invention are described in thegeneral context of computer-executable instructions, such as routinesexecuted by a general-purpose computer (e.g., a server computer,wireless device, or personal/laptop computer). Those skilled in therelevant art will appreciate that the invention can be practiced withother communications, data processing, or computer systemconfigurations, including Internet appliances, hand-held devices(including personal digital assistants (PDAs)), wearable computers, allmanner of cellular or mobile phones, embedded computers (including thosecoupled to vehicles), multi-processor systems, microprocessor-based orprogrammable consumer electronics, set-top boxes, network PCs,mini-computers, mainframe computers, and the like. Indeed, the terms“computer,” “host,” and “host computer” are generally usedinterchangeably and refer to any of the above devices and systems, aswell as any data processor.

Aspects of the invention can be embodied in a special purpose computeror data processor that is specifically programmed, configured, orconstructed to perform one or more of the computer-executableinstructions explained in detail herein. Aspects of the invention canalso be practiced in distributed computing environments where tasks ormodules are performed by remote processing devices, which are linkedthrough a communication network. In a distributed computing environment,program modules may be located in both local and remote memory storagedevices.

Aspects of the invention may be stored or distributed oncomputer-readable media, including magnetically or optically readablecomputer disks, as microcode on semiconductor memory, nanotechnologymemory, organic or optical memory, or other portable data storage media.Indeed, computer-implemented instructions, data structures, screendisplays, and other data under aspects of the invention may bedistributed over the Internet or over other networks (including wirelessnetworks), on a propagated signal on a propagation medium (e.g., anelectromagnetic wave(s), a sound wave, etc.) over a period of time, ormay be provided on any analog or digital network (packet switched,circuit switched, or other scheme). Those skilled in the relevant artwill recognize that portions of the invention reside on a servercomputer, while corresponding portions reside on a client computer, suchas a mobile device.

Referring to FIG. 1, a MAMR system 100 on which the out of route meterread identification and graphical route playback can be implementedprovides various networked components. The system 100 is an example ofone arrangement of elements, but others are possible. The system 100includes a collection of utility meters (102, 104, and 106). The utilitymeters may be of the same or different types (e.g., electric 102, gas104, water 106, or other (not shown)). The utility meters (102, 104, and106) may be distributed in a bounded or unbounded geographical area.Each utility meter (102, 104, or 106) is connected to or associated witha utility consuming facility (not shown). For example, a utility metermay correspond with a household, a commercial facility, or anotherutility consuming facility or device.

While not illustrated in detail, each meter (102, 104, or 106) includesa storage component (not shown) for storing collected data beforetransmission to a data collection system. The storage component may alsostore information identifying the meter, such as a meter address. Inaddition, each meter may be configured with a receiver/transmittertelemetry device (e.g., ERT) capable of sending and receiving signals toand from a mobile data collection system 108. In general, thesecomponents (meter, storage, and telemetry device) may be collectivelyreferred to as an “endpoint.” However, the term “endpoint” may hereinrefer to any one of a number of possible configurations for locallycollecting data, such as utility consumption data, and not only thesample configuration described above.

In some embodiments, the mobile data collection system 108 may send awake-up signal to an endpoint. The received wake-up signal prompts theendpoint to transmit meter reading data to the mobile data collectionsystem 108. In alternative embodiments, “bubble-up” (broadcast)techniques may be used instead of the “wake-up” technique describedabove. In yet other embodiments, the mobile data collection system 108may be capable of point-to-point communications with specific endpoints.

To facilitate MAMR or similar techniques, the mobile data collectionsystem 108 may be installed in a vehicle 109 or be otherwise configuredto be transported through a route. For example, the vehicle may includethe appropriate antennas, power cables, mounts, etc.

The system 100 also includes a host processing system and meter readingapplication(s) 110 for processing collected meter reading data. The hostprocessing system and meter reading application(s) 110 may be operatingin association with systems operated by a utility company, such as autility billing system 112 or, more generally, a customer informationsystem (CIS). In this way, the host processing system and meter readingapplication 110 can also be used to communicate data to the datacollection system 108. This information may include standard route data.In general, the meter reading application uses customer informationdownloaded, for example, to create a route file used when driving theroute to collect meter data. The collected data is returned to the meterreading application for processing. Examples of meter readingapplications may include MV-RS™, Premierplus4™, Viena™, and Integrator™,all by Itron, Inc. of Spokane, Wash.

Referring to FIG. 2, the mobile data collection system 108 of FIG. 1 isshown in more detail. A mobile collector applications component 204maintains route-related meter reading statistics, provides operatingstatus information, and stores, processes, formats, and displayscollected data. It may also include administrative functionality thatadministrative users can use to control preferences and settings of thedata collection system.

A processor 206 and memory or other data storage 208 providecapabilities to control several processes, including management ofcollected meter reading data and processing of input for purposes ofdetermining an efficient route for meter reading. For example, thememory 208 can store not only collected meter data, but also route andother information. A CD ROM 209 may handle removable media in the mobiledata collection system 108. A user input/output component 210 providesan appropriate user interface for an operator of the data collectionsystem 108. For example, the mobile data collection system 108 mayprovide a color touch screen display for ease of use and clear graphicalmapping displays. Other user input/output options may be used includingmouses, microphones, speakers, joysticks, keyboards, LCD screens, audio,etc.

One application of the input/output component 210 includes displayingand controlling mapping images generated by a mapping component 212. Inthis way, the operator is provided with feedback, so that he or she candetermine which meter readings have been completed on a particular routeand so he or she can view meters on the route in relation to the vehicleand to other meters. The mapping component 212 may interface with themobile collector applications component 204.

Any one of the components described above may be contained on notebookcomputer or other device that can be easily removed from the vehiclewhen not in use, such as the Itronix GoBook MAX™.

In some embodiments, route data may be transferred to and from themobile data collection system 108 using a removable flash card 213. Forexample, an operating system (not shown) associated with the mobile datacollection system 108 may recognize the flash card 213 as a removabledrive, allowing standard file access. In other embodiments, the routesmay be transferred to the mobile data collection system via a local areanetwork (LAN), a wide area network (WAN), etc. Periodic data backups tothe flash card can be configured in the mobile collector applicationscomponent 204.

The mobile data collection system 108 also includes a radio based remotereading component 214, which, in some embodiments, may include atransceiver. The radio based remote reading component 114 may, via aradio antenna 215, send signals to wake-up meters that function in“wake-up” mode and to receive and manage incoming data. The mobile datacollection system 108 may also include a Global Positioning System (GPS)component 216, a Global Information Services (GIS) component 218, orlike systems, which may be used to facilitate mapping and other relatedfunctionality, such as route playback features.

In general, GPS uses a network of satellites that continuously transmitcoded information that makes it possible to precisely triangulatelocations on earth by measuring the distance from satellites. GPSsignals broadcast line of sight, meaning that the signals will passthrough clouds, glass, and plastic but will not pass through most solidobjects, including people, buildings, and mountains. The GPS receiverprovides increased accuracy of positioning data as the number ofaccessible satellites increases. Accordingly, aspects of the mappingcomponent can be configured to inform the operator of the number ofsatellites available.

Where the GPS component 216 (or GIS component 218) is implemented,operators of the mobile data collection system 108 can use latitude andlongitude coordinates to locate endpoints in the field and to track theprogress of the mobile collection vehicle while driving the route. Thisinformation may also be used in implementing a playback feature, whichis described in more detail below with respect to FIGS. 9-12. In someembodiments, the GPS component 216 uses embedded mapping software to mapthe GPS coordinates in any given area (including geography, roads,landmarks, etc.). In some embodiments, an endpoint location file (shownas input 220) provided to the mobile data collection system 108 providesinformation on endpoint locations.

III. User Interface

Various user screens, views, and other interfaces may allow users tomonitor and manage meter reading route activities. Examples of suchscreens are described with respect to FIGS. 3-12. While only certainexamples are given, a person skilled in the art will appreciate thatmany other interfaces could be implemented without departing from thescope of the invention. The terms “view,” “screen,” “window,” and “page”are generally used interchangeably herein. The pages described hereinmay be implemented using, for example, WML (wireless markup language),XHTML (extensible hypertext markup language), XML (extensible markuplanguage), or HTML (hypertext markup language). In some embodiments, WMLand XHTML decks offer similar functionality but may differ with respectto style guide and design requirements between the two languages (use ofcolor, icons, etc.).

In some cases, the screens or pages provide facilities to receive inputdata, such as a form with fields to be filled in, pull-down menus orentries allowing one or more of several options to be selected, buttons,sliders, hypertext links, or other known user interface tools forreceiving user input. While certain ways of displaying information tousers are shown and described with respect to certain Figures, thoseskilled in the relevant art will recognize that various otheralternatives may be employed. The terms “screen,” “web page,” and “page”are generally used interchangeably herein. The pages or screens arestored and/or transmitted as display descriptions, as graphical userinterfaces, or by other methods of depicting information on a screen(whether personal computer, PDA, mobile telephone, or other) where thelayout and information or content to be displayed on the page are storedin memory, database, or other storage facility.

When implemented as web pages or wireless content, the screens arestored as display descriptions, graphical user interfaces, or othermethods of depicting information on a computer screen (e.g., commands,links, fonts, colors, layout, sizes and relative positions, and thelike), where the layout and information or content to be displayed onthe page are stored in a database. In general, a “link” refers to anyresource locator identifying a resource on a network, such as a displaydescription provided by an organization having a site or node on thenetwork. A “display description,” as generally used herein, refers toany method of automatically displaying information on a computer screenin any of the above-noted formats, as well as other formats, such asemail or character/code-based formats, algorithm-based formats (e.g.,vector generated), or matrix or bit-mapped formats. While aspects of theinvention are described herein using a networked environment, some orall features may be implemented within a single-computer environment.

In general, for ease in describing features of the invention, aspects ofthe invention will now be described in terms of a user (e.g., a mobiledata collection system operator) interacting with the mobile datacollection system.

A. System Performance Monitoring

Referring to FIG. 3, a dashboard view 300 allows a user to monitorcurrent (e.g., over the last minute) system performance while collectingmeter reads. A view tool bar 302 provides access to other systemfunctionality via a set of buttons. For example, a mapping button 304provides access to mapping functionality that displays a graphic view ofthe route showing each endpoint or group of endpoints on a map of ameter reading area (described in detail with respect to FIGS. 4-7). Aremaining button 306 may provide access to functionality that displaysthe endpoints that still need to be read in a route. A tamper changebutton 308 may provide access to functionality that displays collectedreads that contain a change to their tamper status. An out of routebutton 310 may provide access to functionality that displays informationabout reads collected for endpoints that are not included in loadedroute files (described in detail with respect to FIG. 8). An incomingbutton 312 may provide access to functionality that dynamically displayseach new reading as the system collects it. A segment summary button 314may provide access to functionality that monitors the progress of routesby segment including segment-specific messages. A route summary button316 may provide access to functionality that displays a view of theroutes that are currently loaded in the system, the total number ofendpoints in the route, the percentage of endpoints that have been readalready, and the primary and secondary status of the route. A dashboardbutton 318 provides access to the dashboard view 300 from other screensor views.

In the illustrated embodiment, the dashboard view 300 provides acontinuously updated summary of data collection system performance.Performance indicators can include the number of reads per minute 320,error or alert messages 322, the amount of free space available on abackup disk 324, the frequency and tones that the system is transmittingto read meters 326, the number of satellites available to a mappingsystem 328, etc. In addition, the dashboard view 300 may provide anindication of a current GPS position 330 of the vehicle.

In the illustrated embodiment, the reads per minute feature 320 showsthe total number of new in route and out of route reads collected withina given time frame (e.g., over the last 60 seconds) in aspeedometer-like display that refreshes periodically (e.g., every 15seconds). The session alerts feature 322 displays the total number ofuncleared alerts that is in an audit log, as well as the most severealert that is currently active. In some embodiments, a bar (not shown)below the session alerts feature displays a color-coded warning,depending on the severity of the highest priority alert. For example,red may indicate a critical alert that requires immediate action, whileorange may notify of a temporary malfunction or loss of data and yellowmay indicate a condition where no immediate action is needed.

In some embodiments, the dashboard view may be displayed alone, while inother embodiments, it may be displayed in addition to other screens orviews, such as a route mapping view.

B. Route Mapping

Referring to FIGS. 4-7, a user may monitor route reading progress usinga mapping view 500. The mapping view 500 allows the user to see thevehicle's location and the changing status (e.g., unread, read, out ofroute, etc.) of route endpoints as travel over a route progresses. Amapping symbology key 400 is shown in FIG. 4, and provides samplesymbols for a single unread endpoint (single red dot) 402, groups ofunread endpoints (single red dot with white in the middle) 404,duplicate endpoints (red dot with white cross) 406, a single readendpoint (single green triangle) 408, groups of read endpoints (singlegreen triangle with white in the middle) 410, a vehicle with a good GPSsignal 412, and a vehicle without a good GPS signal 414. As illustrated,endpoints in close proximity are displayed as groups (404 and 410).Proximity for grouping varies depending on the zoom level of the mapand, possibly, grouping settings. Endpoints are duplicates 406 if thesame endpoint ID exists more than once in the system, either in the sameroute file or in multiple routes. In the illustrated embodiment, if asfew as one endpoint in the group is unread, the group is displayed as agroup of unread endpoints.

The mapping symbology also includes symbols for unread out of routeendpoints (blue rectangle) 416 and read out of route endpoints (bluerectangle with white in the middle) 418.

FIG. 5 provides an example of a mapping view 500 showing an applicationof the symbology introduced in FIG. 4. For example, many different typesof endpoints are shown, including single read endpoints, single unreadendpoints, single groups of read endpoints, single groups of unreadendpoints, and the vehicle. In the illustrated embodiment, the map isdynamic, meaning that it changes as the meter reading route progresses.For example, unread endpoints may change to read endpoints as readingsoccur, and new endpoints may appear on the map as they come into range.In addition, the mapping may provide information about the order ortiming of a communication with an endpoint. For example, the most recentendpoints (e.g., most recently read) may appear in a bright resolutionwhile the older endpoints (e.g., least recently read) may appearslightly faded.

Out of route endpoints also appear on the map, allowing the operator ofthe vehicle to make decisions on how to progress on the route (e.g.,which street to turn on next). For example, if significant numbers ofout of route endpoints are appearing on the map, this signals to thedriver that he or she is nearing the edge or border of a route, and mayneed to change course.

In some embodiments, the map may be interactive by allowing users todrill down on specific endpoints. For example, clicking on or touchingan out of route endpoint on the map may result in the display ofspecific information regarding the out of route endpoint, such as thespecific information described with respect to FIG. 8.

Referring to FIG. 6 the mapping view 500 may provide several ways tomove around the map (e.g., up and down, side to side, diagonally, etc.).In some embodiments, the mapping feature uses software such asMicrosoft's MapPoint 2004 engine, which provides maps for North America.However, many other implementations are possible. Navigation controls602 on the top, bottom, sides, and corners of the map allow the user tomove the map up, down, side to side, and diagonally. In someembodiments, an auto pan feature may be available, which enables movingof the map as the vehicle moves. The auto pan feature may be selectedusing an auto pan button 604. A full map screen button 606 may be usedto toggle between a full screen view and a navigation mode. In someembodiments, a map filtering may be used to view map data that matchesgiven search criteria. The map filtering may be accessed from a filteroption button 608.

Referring to FIG. 7, the mapping functionality may also provide forzooming capability so that users can change the altitude or detail levelof the map. In some embodiments, a user zooms in a selected portion ofthe map by dragging an adjustable size box 702 around the map display toa selected area. In the illustrated embodiment, the size of the box(selected area) determines the zoom level. Other techniques for zoomingin and out may be used, such as a zoom size toolbar 704.

In some embodiments, the mapping functionality described herein may becombined with other functionality including voice enhancements, layeringof maps to portray varying levels of detail (e.g., utilityinfrastructure vs. meters), or varying meter types (e.g., gas vs.electric vs. water), etc. Many combinations and features are possible.

C. Out of Route Meters

Referring to FIG. 8, an out of route 800 view may include a staticdisplay that shows collected reads that do not belong to any of theroutes currently loaded in the mobile collection system database. Byproviding information about out of route endpoints, routes can bereconfigured and updated on an ongoing basis to improve efficiency. Forexample, if there is a new house on a route that results in an out ofroute read when the driver passes through the area using the mobilecollection system, the mobile data collection system can provide thisinformation to the utility, so that it can be used to modify the route.In general, the out of route view 800 provides a visual graphicaldisplay that tells the driver when the system is performing an out ofroute meter read.

In some embodiments, the out of route view 800 may use informationcontained in the route file received from the utility or other source.In some embodiments, the mobile data collector captures the vehicle'slocation at the time the out of route endpoint was read, while anyprocessing of the data may be performed remotely (e.g., at the hostprocessor of FIG. 1). Information regarding out of route reads may bestored at the remote processing location for a period of time so thatthe utility can query a history of reads and avoid having to conduct areread after a corresponding route for the out of route meter isconfirmed.

In some embodiments, the out of route view 800 includes a list portion802 and a properties portion 804, so that users can compare multiplereads simultaneously (via the list portion 802) or focus on a singleread (via the properties portion 804). A default sort order in the listportion 802 displays out of route reads by the time collected, beginningwith the most recent and continuing in descending order. The out ofroute view 800 may show an endpoint ID 806, a latest endpoint readingfor the endpoint 808 (e.g., kilowatt hours used), a message count forthe endpoint 810 (e.g., the number of times the endpoint was heard atthe time the reading was collected), a reading time 812, and an endpointtype 814 (e.g., ERT type), as reported by the endpoint.

The out of route view 800 may also provide information on the locationof the out of route endpoint, and the location of the vehicle at thetime it read the out of route endpoint. More specifically, the out ofroute view may provide endpoint latitude data 816, endpoint longitudedata 818, vehicle latitude data 820, and vehicle longitude data 822. Tofacilitate the collection, storage, processing, and display of out ofroute endpoints, this information may be contained within one or moredata structures. In addition, the data structures may includeinformation used to facilitate the mapping the out of route endpoints(shown, for example, in FIG. 5) or presenting the out of route endpointsin a route playback feature (as described with respect to FIGS. 9-12.

Based on the information related to out of out endpoints, the mobiledata collection system may automatically determine an optimized drivingpath for the operator of the vehicle to take. This may be implementedusing various mathematical computations and/or algorithms associatedwith the route and the geographic locations of the out of routeendpoints. After the route is completed, the mobile data collectionsystem may provide stored information relating to the out of routeendpoints to a host processing system, or other system, where theinformation may go through additional processing. The utility serviceprovider may then use this information to reconfigure or optimize meterreading routes and to otherwise increase the efficiency of the mobilecollection system. For example, the information related to out of routemeters may be used to automatically determine which endpoints to includewithin predetermined routes, thus reducing the number of out of routeendpoints encountered on each route.

Other aspects of the user interface for out of route endpoints includesoptional alerts that alert the operator of out of route endpoints whilea route is being driven. Examples of alert sounds include high beeps,low beeps, rings, bells, etc. In the illustrated embodiment, a series ofbeep configuration choices are available to the user by selection of aradio button.

While the illustrated examples show out of route endpoints in a MAMRsystem, one skilled in the art will recognize that similar techniquescan be implemented in fixed network meter reading systems and othersystems without departing from the scope of the invention. Fixed networkmeter reading systems may include wireless and or wire line transmissionof meter reading data over large areas without the use of a vehicle orother localized collection techniques.

D. Route Playback

Referring to FIGS. 9-12, a route playback component allows a user (e.g.,a supervisor) to replay a driver's route. More specifically, it allowsthe user to see exactly how the driver drove the route, which meterswere read, the timing of meter reads, the order of meter reads, etc. Insome embodiments, the routes may be made up of segments and the routeplayback component allows the user to view one segment of the route at atime. The route playback component can have many uses, includingreviewing routes for driving efficiency, troubleshooting missingendpoints, monitoring route drivers, investigating the occurrence of outof route readings, training, creating new routes, etc.

The route playback component may be implemented, in part, using alogging feature that tracks the progress of the vehicle as it drives aroute. As shown in FIG. 9, the user can play back a route from aplayback view by first importing a route file (e.g., .tlr) from a logdirectory.

As shown in FIGS. 10 and 11, to start the playback in a correspondingplayback view 1000, the user selects a play/pause button 1002, causingthe route to play back, and showing the driving path as a colored line1004. As with the mapping view of FIGS. 4-7, the user may use navigationcontrols 1102 to move the map up and down, side to side, and diagonally.The playback view 1000 may also have zoom features 1104. The user maypause the playback using the pause/play button 1002 or stop the playbackusing a stop button 1105. In addition, a progress bar 1106 shows theprogress of the vehicle on the route. In some embodiments, the user mayslide the vehicle icon progress bar 1106 to jump to a specific part ofthe route. In some embodiments, the playback speed can be adjusted torange from slow to fast using a playback speed adjustment bar 1108.Indicators of time since the route began 1110, number of satellitesacquired 1112, vehicle/van speed 1114, and current system time 1116 mayalso be provided.

While not shown in detail in FIGS. 10 and 11, the playback may includeshowing graphical depictions of the various endpoints (both in routeendpoints and possibly out of route endpoints) in the order and timingthat the mobile data collection system read and acknowledged them.Examples of such graphical depictions are shown with respect to FIGS.5-7. An example of the symbology used for such depictions is shown withrespect to FIG. 4. However, other depictions are possible, includingdepictions that use color, sounds, fading, animation, etc.

In some embodiments, like the mapping features shown with respect toFIGS. 5-7, the user may be able to drill down for details of specificendpoints by selecting the pause/play button 1002, and then clicking ortouching the endpoints shown on the screen.

Referring to FIG. 12, the information used to implement the routeplayback may be contained in a data structure 1200. In some embodiments,the data structure may include a header 1202 (e.g.,ITRON-X74LV5R9C_Administrator_(—)2003-07-03) that is comprised of thecurrent user (e.g., Windows user) and the current date. The datastructure 1200 may also include a UTCTime component 1204 (e.g., 213355),a LocalTime component 1206 (e.g., Jul. 3, 2004 2:32:23 PM), a Latitudecomponent 1208 (e.g., 47.6835316666667), a Longitude component 1210(e.g., −117.195015), a Satellites component 1212 that provides a numberof available satellites (e.g., 6), a Speed component 1214 that providesthe speed of the vehicle when taking the reading (e.g., 35), a Directioncomponent 1216 that provides the direction of the vehicle when takingthe reading (e.g., direction in terms of degrees), etc.

IV. System Flows

FIGS. 13-15 are representative flow diagrams that show processes thatoccur within the system of FIG. 1. These flow diagrams do not show allfunctions or exchanges of data but, instead, provide an understanding ofcommands and data exchanged under the system. Those skilled in therelevant art will recognize that some functions or exchanges of commandsand data may be repeated, varied, omitted, or supplemented, and otheraspects not shown may be readily implemented. For example, while notdescribed in detail, a message containing data may be transmittedthrough a message queue, over HTTP, etc.

Referring to FIG. 13, the mobile data collection system may perform aroutine 1300 for identifying, collecting, and providing informationabout out of route endpoints encountered on a route. In someembodiments, the routine 1300 takes place while a MAMR route is beingperformed. In alternate embodiments, the routine 1300 takes place duringdata collection in a fixed network automatic meter reading system. Atblock 1301 the routine 1300 receives a next endpoint reading containinginformation associated with an endpoint. The endpoint information mayinclude an identifier for the endpoint, meter reading data, meter tamperdata, etc. The received endpoint information may also includeinformation about the endpoint's location, including the endpoint'saddress or GPS coordinates. This information may be received within asingle data structure or within a combination of data structures. Insome embodiments, this information is known locally at the mobile datacollection system and/or at a host processing system.

At decision block 1302, the routine 1300 determines whether the endpointis an out of route endpoint (e.g., whether it is associated with thecurrent route, whether it is associated with a route known by the mobilecollection system, etc.). If at decision block 1302 the routine 1300determines that the endpoint is not an out of route endpoint, theroutine 1300 continues at block 1305, where the routine records and/ordisplays the information for an in route endpoint. If, however, atdecision block 1302 the routine 1300 determines that the endpoint is anout of route endpoint, the routine continues at block 1303, where itrecords the received information for the out of route endpoint. Inaddition, the routine 1300 may record information about the location ofthe vehicle at the time the out of route endpoint was read. Thisinformation may be stored within a single data structure or within acombination of data structures.

At block 1304 the routine 1300 provides an indication of the out ofroute endpoint to the operator of the mobile data collection system. Forexample, the routine 1300 may show the out of route endpoint on a map,sound an alert when the out of route endpoint is read, add the out ofroute endpoint to a displayed list of out of route endpoints, or providespecific textual information for the out of route endpoint.

At block decision block 1306 the routine 1300 checks whether the routeis completed (e.g., all meters on the route have been read). If theroute is completed, the routine continues at block 1307, where theroutine transmits completed route information to the host processingsystem. The routine 1300 then ends. If, however, at decision block 1306,the route is not completed, the routine 1300 loops back to block 1301 toreceive the next endpoint reading.

Referring to FIG. 14, the mobile data collection system may perform aroutine 1400 for logging route events for use with a graphical playbacktool that shows a mapping of the vehicle traveling the route and theroute's endpoints as the mobile data collection system establishescommunication with such endpoints. At block 1401 the routine 1400records the vehicle's location at a time t. At block 1402, the routine1400 identifies communications with endpoints made between time t and aprevious time (t−1). The identified communications may include receivinga wake-up signal response from an endpoint, reading an endpoint, etc. Atblock 1403 the routine 1400 records information associated with theidentified communications. The recorded information may includeinformation about the ID, location, status, and/or reading of each ofthe endpoints associated with the identified communications. Thisinformation may be recorded using a single data structure or acombination of data structures.

At decision block 1404 the routine 1400 checks whether the route iscompleted (e.g., all meters on the route have been read). If the routeis completed, the routine 1400 continues at block 1405, where theroutine transmits the recorded route information to the host processingsystem (e.g., in the form of a log file). The routine 1400 then ends.If, however, at decision block 1404, the route is not completed, thetime t is set to equal (t+1) and the routine 1400 loops back to block1401 to record the next vehicle location.

Referring to FIG. 15, a routine 1500 for playback of a graphical displayshowing a mobile data collection system performing a meter reading routemay be performed at a device configured for displaying maps or similarinformation and for executing a log file containing route information.At block 1501, the routine 1500 receives a user request to execute aselected route file. At block 1502, the routine 1500 imports theselected route file. An example of this is shown with respect to FIG.10. For example, the routine 1500 may import the selected route filefrom a host processing system. At block 1503, the routine 1500 loads amap associated with the selected route file. At block 1504, the routine1500 receives a user request to start the route playback. For example,the user may select a play button to initiate the request. At block1505, the routine 1500 plays back the graphical display on the route. Anexample of this is shown with respect to FIGS. 10 and 11. The routine1500 then ends.

V. Conclusion

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” Additionally, the words “herein,”“above,” “below,” and words of similar import, when used in thisapplication, shall refer to this application as a whole and not to anyparticular portions of this application. When the claims use the word“or” in reference to a list of two or more items, that word covers allof the following interpretations of the word: any of the items in thelist, all of the items in the list, and any combination of the items inthe list.

The above detailed description of embodiments of the invention is notintended to be exhaustive or to limit the invention to the precise formdisclosed above. While specific embodiments of, and examples for, theinvention are described above for illustrative purposes, variousequivalent modifications are possible within the scope of the invention,as those skilled in the relevant art will recognize. For example, whileprocesses or blocks are presented in a given order, alternativeembodiments may perform routines having steps, or employ systems havingblocks, in a different order, and some processes or blocks may bedeleted, moved, added, subdivided, combined, and/or modified. Each ofthese processes or blocks may be implemented in a variety of differentways. Also, while processes or blocks are at times shown as beingperformed in series, these processes or blocks may instead be performedin parallel, or may be performed at different times. Where the contextpermits, words in the above Detailed Description using the singular orplural number may also include the plural or singular number,respectively.

The teachings of the invention provided herein can be applied to othersystems, not necessarily the system described herein. The elements andacts of the various embodiments described above can be combined toprovide further embodiments.

All of the above patents and applications and other references,including any that may be listed in accompanying filing papers, areincorporated herein by reference. Aspects of the invention can bemodified, if necessary, to employ the systems, functions, and conceptsof the various references described above to provide yet furtherembodiments of the invention.

These and other changes can be made to the invention in light of theabove Detailed Description. While the above description details certainembodiments of the invention and describes the best mode contemplated,no matter how detailed the above appears in text, the invention can bepracticed in many ways. Details of the mobile data collection system mayvary considerably in their implementation details, while still beencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing re-defined herein to be restricted to any specificcharacteristics, features, or aspects of the invention with which thatterminology is associated. In general, the terms used in the followingclaims should not be construed to limit the invention to the specificembodiments disclosed in the specification, unless the above DetailedDescription section explicitly defines such terms. Accordingly, theactual scope of the invention encompasses not only the disclosedembodiments, but also all equivalent ways of practicing or implementingthe invention under the claims.

While certain aspects of the invention are presented below in certainclaim forms, the inventors contemplate the various aspects of theinvention in any number of claim forms. For example, while only oneaspect of the invention is recited as embodied in a computer-readablemedium, other aspects may likewise be embodied in a computer-readablemedium. Accordingly, the inventors reserve the right to add additionalclaims after filing the application to pursue such additional claimforms for other aspects of the invention.

1. At a mobile data collection system, a method for providing anindication of out of route endpoints encountered while progressingthrough an automatic meter reading route comprising a plurality ofpredetermined endpoints from which utility consumption data is gathered,the method comprising: receiving meter reading route data providing anindication of each of the predetermined endpoints in the automatic meterreading route; progressing through the automatic meter reading route andcollecting information relating to each of the endpoints detected whileprogressing through the meter reading route, wherein the collectedinformation includes information about the location of the detectedendpoints; for each endpoint for which information is collected,determining whether the endpoint is included in the automatic meterreading route, wherein the determining is based, at least in part, onthe collected information and on the received meter reading route data;if the endpoint is not included in the automatic meter reading route,identifying the endpoint as an out of route endpoint and providing anindication of the out of route endpoint; and, using the identified outof route endpoints to at least in part provide off-cycle billing toutility customers or reconfigure the automatic meter reading route. 2.The method of claim 1 further comprising providing an indication of thelocation of the out of route endpoint, including providing a set oflocation coordinates.
 3. The method of claim 1 further comprisingproviding an indication of the location of the out of route endpoint,including providing a graphical indication displayed on a map.
 4. Themethod of claim 1 further comprising transmitting the indication of theout of route endpoint to a system at a utility provider associated withthe out of route endpoint.
 5. The method of claim 1 wherein theindication of the out of route endpoint is displayed on a list of out ofroute endpoints.
 6. The method of claim 1 further comprising providingdriving directions based on the indication of the out of route endpoint.7. At a mobile data collection system, a method for providing anindication of out-of-route public utility endpoints encountered whileprogressing through a predefined automatic meter reading routecomprising multiple public utility endpoints from which utilityconsumption data is gathered, the method comprising: progressing throughthe predefined automatic meter reading route and wirelessly collectinginformation relating to each of the public utility endpoints detectedwhile progressing through the predefined automatic meter reading route,wherein the wirelessly collected information includes informationidentifying the detected public utility endpoints; for each publicutility endpoint for which information is collected, determining whetherthe public utility endpoint is included in the predefined automaticmeter reading route, wherein the determining is based, at least in part,on the wirelessly collected information and on the predefined automaticmeter reading route; and if the public utility endpoint is not includedin the predefined automatic meter reading route, identifying the publicutility endpoint as an out-of-route public utility endpoint and storingan indication of the out-of-route public utility endpoint for subsequentprocessing.
 8. The method of claim 7 further comprising providing anindication of the location of out-of-route public utility endpoints,including providing a set of location coordinates.
 9. The method ofclaim 7 further comprising providing an indication of the location ofout-of-route public utility endpoints, including providing a graphicalindication displayed on a map.
 10. The method of claim 7 furthercomprising transmitting the indication of the out-of-route publicutility endpoint to a system at a utility provider associated with theout-of-route endpoint.
 11. The method of claim 7 wherein the indicationof the out-of-route public utility endpoint is displayed on a list ofout-of-route public utility endpoints.
 12. The method of claim 7 furthercomprising providing driving directions based on the indication of theout-of-route public utility endpoint.
 13. The method of claim 7 furthercomprising using identified out-of-route endpoints to at least in partproduce off-cycle bills to utility customers or reconfigure thepredefined automatic meter reading route.
 14. In a mobile datacollection system, an apparatus for providing an indication of out ofroute endpoints encountered along an automatic meter reading routehaving multiple predetermined endpoints from which utility consumptiondata is gathered, the apparatus comprising: data storage for storingmeter reading route data, wherein the meter reading route data includesinformation identifying each of multiple endpoints in the automaticmeter reading route, and collected information relating to each of theendpoints detected along the automatic meter reading route, wherein thecollected information includes (a) utility consumption informationcollected from at least some of the detected endpoints, and (b)identification information identifying at least some of the detectedendpoints; and a processor coupled to the data storage, wherein, foreach endpoint for which information is collected, the processor isconfigured to (i) determine whether the endpoint is one of the multipleendpoints in the automatic meter reading route, wherein the determiningis based, at least in part, on the meter reading route and theidentification information identifying at least some of the detectedendpoints in the collected information, and (ii) if the endpoint is notin the automatic meter reading route, then identifying the endpoint asan out of route endpoint, and providing utility consumption informationand identification information for the identified out of route endpoint.15. The apparatus of claim 14 wherein the provided indication of thelocation of the out of route endpoint is a set of location coordinates.16. The apparatus of claim 14, further comprising a wireless receiver,coupled to the processor, for wirelessly receiving the collectedinformation while traveling the automatic meter reading route.
 17. Theapparatus of claim 14 wherein the apparatus is configured to provide theindication of the location of the out of route endpoint to a system at autility provider associated with the out of route endpoint.
 18. Theapparatus of claim 14 wherein at least the processor is a hostprocessing system of a public utility.
 19. The apparatus of claim 14wherein the processor is further configured to provide, via an outputdevice, driving directions based on the indication of the location ofthe out of route endpoint.
 20. A system for gathering data from publicutility nodes encountered while progressing through an automatic meterreading route having multiple selected public utility nodes from whichutility consumption data is gathered, the system comprising: means forstoring meter reading route data associated with each of the multipleselected public utility nodes in the automatic meter reading route;means for collecting information relating to each public utility nodedetected while progressing through the automatic meter reading route,wherein the collected information includes information identifying thedetected public utility nodes; means for determining whether eachdetected public utility node is included in the automatic meter readingroute, wherein the determining is based, at least in part, on thecollected information and on the meter reading route data; and means foridentifying the public utility node as an out-of-route public utilitynode and providing an indication of the out-of-route public utility nodeif the public utility node is determined not to be included in theautomatic meter reading route.
 21. The system of claim 20 furthercomprising means for providing an indication of the location of theout-of-route public utility node.
 22. The system of claim 20 furthercomprising means for providing a graphical indication of the location ofthe out-of-route public utility node.
 23. The system of claim 20 furthercomprising means for transmitting an indication of the out-of-routepublic utility node to a system at a utility provider.
 24. The system ofclaim 20 further comprising means for using the identified out-of-routepublic utility node to at least in part produce off-cycle bills toutility customers.
 25. The system of claim 20 further comprising meansfor using the identified out-of-route public utility node to reconfigurethe automatic meter reading route.
 26. A method for processing data frompublic utility meters encountered while progressing through an automaticmeter reading route having multiple selected utility meters from whichutility consumption data is gathered, the method comprising: storingmeter reading route data associated with each of the multiple selectedutility meters in the automatic meter reading route; receivinginformation relating to each utility meter detected while progressingthrough the automatic meter reading route, wherein the receivedinformation includes information identifying the detected utilitymeters; determining whether each detected utility meter is included inthe automatic meter reading route, wherein the determining is based, atleast in part, on the received information and on the meter readingroute data; and identifying the utility meter as an out-of-route utilitymeter and providing an indication of the out-of-route utility meter ifthe utility meter is determined not to be included in the automaticmeter reading route.